World Wide Web

World Wide Web
Center
The Web's historic logo designed by Robert Cailliau
Inventor Sir Tim Berners Lee[1]
Launch year 1990
Company CERN
Availability Worldwide

The World Wide Web, abbreviated as WWW and commonly known as the Web, is a system of interlinked hypertext documents accessed via the Internet. With a web browser, one can view web pages that may contain text, images, videos, and other multimedia and navigate between them by using hyperlinks. Using concepts from earlier hypertext systems, English engineer and computer scientist Sir Tim Berners-Lee, now the Director of the World Wide Web Consortium, wrote a proposal in March 1989 for what would eventually become the World Wide Web.[1] At CERN in Geneva, Switzerland, Berners-Lee and Belgian computer scientist Robert Cailliau proposed in 1990 to use "HyperText [...] to link and access information of various kinds as a web of nodes in which the user can browse at will",[2] and publicly introduced the project in December.[3]

"The World-Wide Web (W3) was developed to be a pool of human knowledge, and human culture, which would allow collaborators in remote sites to share their ideas and all aspects of a common project." [4]

Contents

History

Arthur C. Clarke was quoted in Popular Science in May 1970, [5] in which he predicted that satellites would one day "bring the accumulated knowledge of the world to our fingertips" using an office console that would combine the functionality of the xerox, telephone, TV and a small computer so as to allow both data transfer and video conferencing around the globe.

In March 1989, Tim Berners-Lee wrote a proposal[6] that referenced ENQUIRE, a database and software project he had built in 1980, and described a more elaborate information management system.

With help from Robert Cailliau, he published a more formal proposal (on November 12, 1990) to build a "Hypertext project" called "WorldWideWeb" (one word, also "W3") as a "web" of "hypertext documents" to be viewed by "browsers" using a client–server architecture.[2] This proposal estimated that a read-only web would be developed within three months and that it would take six months to achieve "the creation of new links and new material by readers, [so that] authorship becomes universal" as well as "the automatic notification of a reader when new material of interest to him/her has become available." See Web 2.0 and RSS/Atom, which have taken a little longer to mature.

The proposal had been modeled after the Dynatext SGML reader by Electronic Book Technology, a spin-off from the Institute for Research in Information and Scholarship at Brown University. The Dynatext system, licensed by CERN, was technically advanced and was a key player in the extension of SGML ISO 8879:1986 to Hypermedia within HyTime, but it was considered too expensive and had an inappropriate licensing policy for use in the general high energy physics community, namely a fee for each document and each document alteration.

This NeXT Computer used by Tim Berners-Lee at CERN became the first web server.
The CERN datacenter in 2010 housing some www servers.

A NeXT Computer was used by Berners-Lee as the world's first web server and also to write the first web browser, WorldWideWeb, in 1990. By Christmas 1990, Berners-Lee had built all the tools necessary for a working Web:[7] the first web browser (which was a web editor as well); the first web server; and the first web pages,[8] which described the project itself. On August 6, 1991, he posted a short summary of the World Wide Web project on the alt.hypertext newsgroup.[9] This date also marked the debut of the Web as a publicly available service on the Internet. The first server outside Europe was set up at SLAC to host the SPIRES-HEP database. Accounts differ substantially as to the date of this event. The World Wide Web Consortium says December 1992,[10] whereas SLAC itself claims 1991.[11][12] This is supported by a W3C document entitled A Little History of the World Wide Web.[13]

The crucial underlying concept of hypertext originated with older projects from the 1960s, such as the Hypertext Editing System (HES) at Brown University, Ted Nelson's Project Xanadu, and Douglas Engelbart's oN-Line System (NLS). Both Nelson and Engelbart were in turn inspired by Vannevar Bush's microfilm-based "memex", which was described in the 1945 essay "As We May Think".

Berners-Lee's breakthrough was to marry hypertext to the Internet. In his book Weaving The Web, he explains that he had repeatedly suggested that a marriage between the two technologies was possible to members of both technical communities, but when no one took up his invitation, he finally tackled the project himself. In the process, he developed a system of globally unique identifiers for resources on the Web and elsewhere: the Universal Document Identifier (UDI), later known as Uniform Resource Locator (URL) and Uniform Resource Identifier (URI); the publishing language HyperText Markup Language (HTML); and the Hypertext Transfer Protocol (HTTP).[14]

The World Wide Web had a number of differences from other hypertext systems that were then available. The Web required only unidirectional links rather than bidirectional ones. This made it possible for someone to link to another resource without action by the owner of that resource. It also significantly reduced the difficulty of implementing web servers and browsers (in comparison to earlier systems), but in turn presented the chronic problem of link rot. Unlike predecessors such as HyperCard, the World Wide Web was non-proprietary, making it possible to develop servers and clients independently and to add extensions without licensing restrictions. On April 30, 1993, CERN announced[15] that the World Wide Web would be free to anyone, with no fees due. Coming two months after the announcement that the Gopher protocol was no longer free to use, this produced a rapid shift away from Gopher and towards the Web. An early popular web browser was ViolaWWW, which was based upon HyperCard.

Scholars generally agree that a turning point for the World Wide Web began with the introduction[16] of the Mosaic web browser[17] in 1993, a graphical browser developed by a team at the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign (NCSA-UIUC), led by Marc Andreessen. Funding for Mosaic came from the U.S. High-Performance Computing and Communications Initiative, a funding program initiated by the High Performance Computing and Communication Act of 1991, one of several computing developments initiated by U.S. Senator Al Gore.[18] Prior to the release of Mosaic, graphics were not commonly mixed with text in web pages and the Web's popularity was less than older protocols in use over the Internet, such as Gopher and Wide Area Information Servers (WAIS). Mosaic's graphical user interface allowed the Web to become, by far, the most popular Internet protocol.

The World Wide Web Consortium (W3C) was founded by Tim Berners-Lee after he left the European Organization for Nuclear Research (CERN) in October, 1994. It was founded at the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) with support from the Defense Advanced Research Projects Agency (DARPA), which had pioneered the Internet; a year later, a second site was founded at INRIA (a French national computer research lab) with support from the European Commission DG InfSo; and in 1996, a third continental site was created in Japan at Keio University. By the end of 1994, while the total number of websites was still minute compared to present standards, quite a number of notable websites were already active, many of which are the precursors or inspiration for today's most popular services.

Connected by the existing Internet, other websites were created around the world, adding international standards for domain names and HTML. Since then, Berners-Lee has played an active role in guiding the development of web standards (such as the markup languages in which web pages are composed), and in recent years has advocated his vision of a Semantic Web. The World Wide Web enabled the spread of information over the Internet through an easy-to-use and flexible format. It thus played an important role in popularizing use of the Internet.[19] Although the two terms are sometimes conflated in popular use, World Wide Web is not synonymous with Internet.[20] The Web is an application built on top of the Internet.

Function

The terms Internet and World Wide Web are often used in every-day speech without much distinction. However, the Internet and the World Wide Web are not one and the same. The Internet is a global system of interconnected computer networks. In contrast, the Web is one of the services that runs on the Internet. It is a collection of interconnected documents and other resources, linked by hyperlinks and URLs. In short, the Web is an application running on the Internet.[21] Viewing a web page on the World Wide Web normally begins either by typing the URL of the page into a web browser, or by following a hyperlink to that page or resource. The web browser then initiates a series of communication messages, behind the scenes, in order to fetch and display it.

First, the server-name portion of the URL is resolved into an IP address using the global, distributed Internet database known as the Domain Name System (DNS). This IP address is necessary to contact the Web server. The browser then requests the resource by sending an HTTP request to the Web server at that particular address. In the case of a typical web page, the HTML text of the page is requested first and parsed immediately by the web browser, which then makes additional requests for images and any other files that complete the page image. Statistics measuring a website's popularity are usually based either on the number of page views or associated server 'hits' (file requests) that take place.

While receiving these files from the web server, browsers may progressively render the page onto the screen as specified by its HTML, Cascading Style Sheets (CSS), or other page composition languages. Any images and other resources are incorporated to produce the on-screen web page that the user sees. Most web pages contain hyperlinks to other related pages and perhaps to downloadable files, source documents, definitions and other web resources. Such a collection of useful, related resources, interconnected via hypertext links is dubbed a web of information. Publication on the Internet created what Tim Berners-Lee first called the WorldWideWeb (in its original CamelCase, which was subsequently discarded) in November 1990.[2]

Linking

Graphic representation of a minute fraction of the WWW, demonstrating hyperlinks

Over time, many web resources pointed to by hyperlinks disappear, relocate, or are replaced with different content. This makes hyperlinks obsolete, a phenomenon referred to in some circles as link rot and the hyperlinks affected by it are often called dead links. The ephemeral nature of the Web has prompted many efforts to archive web sites. The Internet Archive, active since 1996, is one of the best-known efforts.

Dynamic updates of web pages

JavaScript is a scripting language that was initially developed in 1995 by Brendan Eich, then of Netscape, for use within web pages.[22] The standardized version is ECMAScript.[22] To overcome some of the limitations of the page-by-page model described above, some web applications also use Ajax (asynchronous JavaScript and XML). JavaScript is delivered with the page that can make additional HTTP requests to the server, either in response to user actions such as mouse-clicks, or based on lapsed time. The server's responses are used to modify the current page rather than creating a new page with each response. Thus the server only needs to provide limited, incremental information. Since multiple Ajax requests can be handled at the same time, users can interact with a page even while data is being retrieved. Some web applications regularly poll the server to ask if new information is available.[23]

WWW prefix

Many domain names used for the World Wide Web begin with www because of the long-standing practice of naming Internet hosts (servers) according to the services they provide. The hostname for a web server is often www, as it is ftp for an FTP server, and news or nntp for a USENET news server. These host names appear as Domain Name System (DNS) subdomain names, as in www.example.com. The use of such subdomain names is not required by any technical or policy standard; indeed, the first ever web server was called nxoc01.cern.ch,[24] and many web sites exist without a www subdomain, or with some other name such as "www2", "secure", etc. Most web servers are set up such that both the domain root (e.g., example.com) and the www subdomain (e.g., www.example.com) refer to the same site; others require one form or the other, or they may map to different web sites.

When a user submits an incomplete website address to a web browser in its address bar input field, some web browsers automatically try adding the prefix "www" to the beginning of it and possibly ".com", ".org" and ".net" at the end, depending on what might be missing. For example, entering 'microsoft' may be transformed to http://www.microsoft.com/ and 'openoffice' to http://www.openoffice.org. This feature started appearing in early versions of Mozilla Firefox, when it still had the working title 'Firebird' in early 2003.[25] It is reported that Microsoft was granted a US patent for the same idea in 2008, but only for mobile devices.[26]

The scheme specifier (http:// or https://) in URIs refer to the Hypertext Transfer Protocol and to HTTP Secure and so define the communication protocol to be used for the request and response. The HTTP protocol is fundamental to the operation of the World Wide Web, and the encryption involved in HTTPS adds an essential layer if confidential information such as passwords or banking information are to be exchanged over the public Internet. Web browsers usually prepend this scheme to URLs too, if omitted. Berners-Lee has acknowledged that the two forward slashes (//) were originally unnecessary.[27]

In overview, RFC 2396 defines Uniform Resource Indicators to have the following form:

<scheme>://<authority><path>?<query>#<fragment>

Here <authority> is for example the web server (e.g, www.example.com), <path> identifies the web page on that server, from just '/' for the root page to longer paths in the form common on Unix-like operating systems. The web server processes the <query>, which can be data sent via a form, e.g., terms sent to a search engine, and the returned page present the result. Finally, <fragment> is not sent to the web server. It identifies a tag to which the browser positions the page.

In English, www is pronounced by individually pronouncing the name of characters (double-u double-u double-u). Although some technical users pronounce it dub-dub-dub this is not widespread. The English writer Douglas Adams once quipped in The Independent on Sunday (1999): "The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it's short for," with Stephen Fry later pronouncing it in his "Podgrammes" series of podcasts as "wuh wuh wuh." In Mandarin Chinese, World Wide Web is commonly translated via a phono-semantic matching to wàn wéi wǎng (万维网), which satisfies www and literally means "myriad dimensional net",[28] a translation that very appropriately reflects the design concept and proliferation of the World Wide Web. Tim Berners-Lee's web-space states that World Wide Web is officially spelled as three separate words, each capitalized, with no intervening hyphens.[29]

Privacy

Computer users, who save time and money, and who gain conveniences and entertainment, may or may not have surrendered the right to privacy in exchange for using a number of technologies including the Web.[30] Worldwide, more than a half billion people have used a social network service,[31] and of Americans who grew up with the Web, half created an online profile[32] and are part of a generational shift that could be changing norms.[33][34] Facebook progressed from U.S. college students to a 70% non-U.S. audience, and in 2009 estimated that only 20% of its members use privacy settings.[35] In 2010 (six years after co-founding the company), Mark Zuckerberg wrote, "we will add privacy controls that are much simpler to use".[36]

Privacy representatives from 60 countries have resolved to ask for laws to complement industry self-regulation, for education for children and other minors who use the Web, and for default protections for users of social networks.[37] They also believe data protection for personally identifiable information benefits business more than the sale of that information.[37] Users can opt-in to features in browsers to clear their personal histories locally and block some cookies and advertising networks[38] but they are still tracked in websites' server logs, and particularly web beacons.[39] Berners-Lee and colleagues see hope in accountability and appropriate use achieved by extending the Web's architecture to policy awareness, perhaps with audit logging, reasoners and appliances.[40]

In exchange for providing free content, vendors hire advertisers who spy on Web users and base their business model on tracking them.[41] Since 2009, they buy and sell consumer data on exchanges (lacking a few details that could make it possible to de-anonymize, or identify an individual[42]).[41] Hundreds of millions of times per day, Lotame Solutions captures what users are typing in real time, and sends that text to OpenAmplify who then tries to determine, to quote a writer at The Wall Street Journal, "what topics are being discussed, how the author feels about those topics, and what the person is going to do about them".[43][44]

Microsoft backed away in 2008 from its plans for strong privacy features in Internet Explorer,[45] leaving its users (60% of the world's Web users) open to advertisers who may make assumptions about them based on only one click when they visit a website.[46] Among services paid for by advertising, Yahoo! could collect the most data about users of commercial websites, about 2,500 bits of information per month about each typical user of its site and its affiliated advertising network sites. Yahoo! was followed by MySpace with about half that potential and then by AOLTimeWarner, Google, Facebook, Microsoft, and eBay.[47]

Security

The Web has become criminals' preferred pathway for spreading malware. Cybercrime carried out on the Web can include identity theft, fraud, espionage and intelligence gathering.[48] Web-based vulnerabilities now outnumber traditional computer security concerns,[49][50] and as measured by Google, about one in ten web pages may contain malicious code.[51] Most Web-based attacks take place on legitimate websites, and most, as measured by Sophos, are hosted in the United States, China and Russia.[52] The most common of all malware threats is SQL injection attacks against websites.[53] Through HTML and URIs the Web was vulnerable to attacks like cross-site scripting (XSS) that came with the introduction of JavaScript[54] and were exacerbated to some degree by Web 2.0 and Ajax web design that favors the use of scripts.[55] Today by one estimate, 70% of all websites are open to XSS attacks on their users.[56]

Proposed solutions vary to extremes. Large security vendors like McAfee already design governance and compliance suites to meet post-9/11 regulations,[57] and some, like Finjan have recommended active real-time inspection of code and all content regardless of its source.[48] Some security vendors like Commtouch monitor new threats and provide reporting tools for malware outbreaks, spam, and zombie trends along with real-time outbreak monitors.[58]

Some have argued that for enterprise to see security as a business opportunity rather than a cost center,[59] "ubiquitous, always-on digital rights management" enforced in the infrastructure by a handful of organizations must replace the hundreds of companies that today secure data and networks.[60] Jonathan Zittrain has said users sharing responsibility for computing safety is far preferable to locking down the Internet.[61]

Standards

Many formal standards and other technical specifications and software define the operation of different aspects of the World Wide Web, the Internet, and computer information exchange. Many of the documents are the work of the World Wide Web Consortium (W3C), headed by Berners-Lee, but some are produced by the Internet Engineering Task Force (IETF) and other organizations.

Usually, when web standards are discussed, the following publications are seen as foundational:

Additional publications provide definitions of other essential technologies for the World Wide Web, including, but not limited to, the following:

Accessibility

Access to the Web is for everyone regardless of disability including visual, auditory, physical, speech, cognitive, or neurological. Accessibility features also help others with temporary disabilities like a broken arm or the aging population as their abilities change.[62] The Web is used for receiving information as well as providing information and interacting with society, making it essential that the Web be accessible in order to provide equal access and equal opportunity to people with disabilities.[63] Tim Berners-Lee once noted, "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."[62] Many countries regulate web accessibility as a requirement for websites.[64] International cooperation in the W3C Web Accessibility Initiative led to simple guidelines that web content authors as well as software developers can use to make the Web accessible to persons who may or may not be using assistive technology.[62][65]

Internationalization

The W3C Internationalization Activity assures that web technology will work in all languages, scripts, and cultures.[66] Beginning in 2004 or 2005, Unicode gained ground and eventually in December 2007 surpassed both ASCII and Western European as the Web's most frequently used character encoding.[67] Originally RFC 3986 allowed resources to be identified by URI in a subset of US-ASCII. RFC 3987 allows more characters—any character in the Universal Character Set—and now a resource can be identified by IRI in any language.[68]

Statistics

According to a 2001 study, there were massively more than 550 billion documents on the Web, mostly in the invisible Web, or deep Web.[69] A 2002 survey of 2,024 million Web pages[70] determined that by far the most Web content was in English: 56.4%; next were pages in German (7.7%), French (5.6%), and Japanese (4.9%). A more recent study, which used Web searches in 75 different languages to sample the Web, determined that there were over 11.5 billion Web pages in the publicly indexable Web as of the end of January 2005.[71] As of March 2009, the indexable web contains at least 25.21 billion pages.[72] On July 25, 2008, Google software engineers Jesse Alpert and Nissan Hajaj announced that Google Search had discovered one trillion unique URLs.[73] As of May 2009, over 109.5 million websites operated.[74] Of these 74% were commercial or other sites operating in the .com generic top-level domain.[74]

Speed issues

Frustration over congestion issues in the Internet infrastructure and the high latency that results in slow browsing has led to a pejorative name for the World Wide Web: the World Wide Wait.[75] Speeding up the Internet is an ongoing discussion over the use of peering and QoS technologies. Other solutions to reduce the congestion can be found at W3C.[76] Standard guidelines for ideal Web response times are:[77]

Caching

If a user revisits a Web page after only a short interval, the page data may not need to be re-obtained from the source Web server. Almost all web browsers cache recently obtained data, usually on the local hard drive. HTTP requests sent by a browser will usually only ask for data that has changed since the last download. If the locally cached data are still current, it will be reused. Caching helps reduce the amount of Web traffic on the Internet. The decision about expiration is made independently for each downloaded file, whether image, stylesheet, JavaScript, HTML, or whatever other content the site may provide. Thus even on sites with highly dynamic content, many of the basic resources only need to be refreshed occasionally. Web site designers find it worthwhile to collate resources such as CSS data and JavaScript into a few site-wide files so that they can be cached efficiently. This helps reduce page download times and lowers demands on the Web server.

There are other components of the Internet that can cache Web content. Corporate and academic firewalls often cache Web resources requested by one user for the benefit of all. (See also Caching proxy server.) Some search engines also store cached content from websites. Apart from the facilities built into Web servers that can determine when files have been updated and so need to be re-sent, designers of dynamically generated Web pages can control the HTTP headers sent back to requesting users, so that transient or sensitive pages are not cached. Internet banking and news sites frequently use this facility. Data requested with an HTTP 'GET' is likely to be cached if other conditions are met; data obtained in response to a 'POST' is assumed to depend on the data that was POSTed and so is not cached.

See also

  • CERN
  • Deep web
  • Electronic publishing
  • List of websites
  • Streaming media
  • Web 1.0
  • Web 2.0
  • Web accessibility
  • Web archiving
  • Web browser
  • Web directory
  • Web operating system
  • Web science
  • Web search engine
  • Web services
  • Website architecture
  • Website governance
  • Prestel

Notes

  1. 1.0 1.1 "Tim Berners Lee - Time 100 People of the Century". Time Magazine. http://205.188.238.181/time/time100/scientist/profile/bernerslee.html. Retrieved 17 May 2010. "He wove the World Wide Web and created a mass medium for the 21st century. The World Wide Web is Berners-Lee's alone. He designed it. He loosed it on the world. And he more than anyone else has fought to keep it open, nonproprietary and free. ." 
  2. 2.0 2.1 2.2 "Berners-Lee, Tim; Cailliau, Robert (November 12, 1990). "WorldWideWeb: Proposal for a hypertexts Project". http://w3.org/Proposal.html. Retrieved July 27, 2009. 
  3. Berners-Lee, Tim. "Pre-W3C Web and Internet Background". World Wide Web Consortium. http://w3.org/2004/Talks/w3c10-HowItAllStarted/?n=15. Retrieved April 21, 2009. 
  4. Wardrip-Fruin, Noah and Nick Montfort, ed (2003). The New Media Reader. Section 54. The MIT Press. ISBN 0-262-23227-8.
  5. "TV Broadcast Satellite". May 1970. 
  6. "Information Management: A Proposal". March 1989. http://w3.org/History/1989/proposal.html. Retrieved July 27, 2009. 
  7. "Tim Berners-Lee: client". W3.org. http://w3.org/People/Berners-Lee/WorldWideWeb. Retrieved July 27, 2009. 
  8. "First Web pages". W3.org. http://w3.org/History/19921103-hypertext/hypertext/WWW/TheProject.html. Retrieved July 27, 2009. 
  9. "Short summary of the World Wide Web project". Groups.google.com. August 6, 1991. http://groups.google.com/group/alt.hypertext/msg/395f282a67a1916c. Retrieved July 27, 2009. 
  10. "W3C timeline". http://w3.org/2005/01/timelines/timeline-2500x998.png. Retrieved March 30, 2010. 
  11. "About SPIRES". http://slac.stanford.edu/spires/about/. Retrieved March 30, 2010. 
  12. "The Early World Wide Web at SLAC". http://www.slac.stanford.edu/history/earlyweb/history.shtml. 
  13. "A Little History of the World Wide Web". http://www.w3.org/History.html. 
  14. "Inventor of the Week Archive: The World Wide Web". Massachusetts Institute of Technology: MIT School of Engineering. http://web.mit.edu/invent/iow/berners-lee.html. Retrieved July 23, 2009. 
  15. "Ten Years Public Domain for the Original Web Software". Tenyears-www.web.cern.ch. April 30, 2003. http://tenyears-www.web.cern.ch/tenyears-www/Welcome.html. Retrieved July 27, 2009. 
  16. "Mosaic Web Browser History - NCSA, Marc Andreessen, Eric Bina". Livinginternet.com. http://livinginternet.com/w/wi_mosaic.htm. Retrieved July 27, 2009. 
  17. "NCSA Mosaic - September 10, 1993 Demo". Totic.org. http://totic.org/nscp/demodoc/demo.html. Retrieved July 27, 2009. 
  18. "Vice President Al Gore's ENIAC Anniversary Speech". Cs.washington.edu. February 14, 1996. http://cs.washington.edu/homes/lazowska/faculty.lecture/innovation/gore.html. Retrieved July 27, 2009. 
  19. "Internet legal definition of Internet". West's Encyclopedia of American Law, edition 2. Free Online Law Dictionary. July 15, 2009. http://legal-dictionary.thefreedictionary.com/Internet. Retrieved November 25, 2008. 
  20. "WWW (World Wide Web) Definition". TechTerms. http://techterms.com/definition/www. Retrieved february 19 2010. 
  21. "The W3C Technology Stack". World Wide Web Consortium. http://www.w3.org/Consortium/technology. Retrieved April 21, 2009. 
  22. 22.0 22.1 Hamilton, Naomi (July 31, 2008). "The A-Z of Programming Languages: JavaScript". Computerworld. IDG. http://computerworld.com.au/article/255293/-z_programming_languages_javascript. Retrieved May 12, 2009. 
  23. Buntin, Seth (23 September 2008). "jQuery Polling plugin". http://buntin.org/2008/sep/23/jquery-polling-plugin/. Retrieved 2009-08-22. 
  24. "Frequently asked questions by the Press - Tim Berners-Lee". W3.org. http://w3.org/People/Berners-Lee/FAQ.html. Retrieved July 27, 2009. 
  25. "automatically adding www.___.com". mozillaZine. May 16, 2003. http://forums.mozillazine.org/viewtopic.php?f=9&t=10980. Retrieved May 27, 2009. 
  26. Masnick, Mike (July 7, 2008). "Microsoft Patents Adding 'www.' And '.com' To Text". Techdirt. http://techdirt.com/articles/20080626/0203581527.shtml. Retrieved May 27, 2009. 
  27. "Berners-Lee 'sorry' for slashes". BBC News. October 14, 2009. http://news.bbc.co.uk/1/hi/technology/8306631.stm. Retrieved March 31, 2010. 
  28. "MDBG Chinese-English dictionary - Translate". http://us.mdbg.net/chindict/chindict.php?page=translate&trst=0&trqs=World+Wide+Web&trlang=&wddmtm=0. Retrieved July 27, 2009. 
  29. "Frequently asked questions by the Press - Tim BL". W3.org. http://w3.org/People/Berners-Lee/FAQ.html. Retrieved July 27, 2009. 
  30. Hal Abelson, Ken Ledeen and Harry Lewis (April 14, 2008). "1–2". Blown to Bits: Your Life, Liberty, and Happiness After the Digital Explosion. Addison Wesley. ISBN 0-13-713559-9. http://bitsbook.com/. Retrieved November 6, 2008. 
  31. comScore (August 12, 2008). "Social Networking Explodes Worldwide as Sites Increase their Focus on Cultural Relevance". Press release. http://comscore.com/press/release.asp?press=2396. Retrieved November 9, 2008. 
  32. Amanda Lenhart and Mary Madden (April 18, 2007). "Teens, Privacy & Online Social Networks" (PDF). Pew Internet & American Life Project. Archived from the original on 2008-03-06. http://web.archive.org/web/20080306031923/http://www.pewinternet.org/pdfs/PIP_Teens_Privacy_SNS_Report_Final.pdf. Retrieved November 9, 2008. 
  33. Schmidt, Eric (Google). (October 20, 2008). Eric Schmidt at Bloomberg on the Future of Technology. New York, New York: YouTube. Event occurs at 16:30. http://youtube.com/watch?v=rD_x9LW5QRg. Retrieved November 9, 2008. 
  34. Nussbaum, Emily (February 12, 2007). "Say Everything". New York (New York Media). http://nymag.com/news/features/27341/. Retrieved November 9, 2008. 
  35. Stone, Brad (March 28, 2009). "Is Facebook Growing Up Too Fast?". The New York Times. http://nytimes.com/2009/03/29/technology/internet/29face.html?pagewanted=all.  and Lee Byron (Facebook) (March 28, 2009). "The Road to 200 Million". The New York Times. http://nytimes.com/imagepages/2009/03/29/business/29face.graf01.ready.html. Retrieved April 2, 2009. 
  36. Zuckerberg, Mark (May 24, 2010). "From Facebook, answering privacy concerns with new settings". The Washington Post. http://www.washingtonpost.com/wp-dyn/content/article/2010/05/23/AR2010052303828.html. Retrieved May 24, 2010. 
  37. 37.0 37.1 "30th International Conference of Data Protection and Privacy Commissioners" (PDF). Press release. October 17, 2008. http://www.privacyconference2008.org/pdf/press_final_en.pdf. Retrieved November 8, 2008. 
  38. Cooper, Alissa (October 2008). "Browser Privacy Features: A Work In Progress" (PDF). Center for Democracy and Technology. http://www.cdt.org/privacy/20081022_browser_priv.pdf. Retrieved November 8, 2008. 
  39. Joshua Gomez, Travis Pinnick, and Ashkan Soltani (June 1, 2009). "KnowPrivacy" (PDF). University of California, Berkeley, School of Information. pp. 8–9. http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf. Retrieved June 2, 2009. 
  40. Daniel J. Weitzner, Harold Abelson, Tim Berners-Lee, Joan Feigenbaum, James Hendler, Gerald Jay Sussman (June 13, 2007). "Information Accountability". MIT Computer Science and Artificial Intelligence Laboratory. http://hdl.handle.net/1721.1/37600. Retrieved November 6, 2008. 
  41. 41.0 41.1 Angwin, Julia (July 30, 2010). "The Web's New Gold Mine: Your Secrets". The Wall Street Journal (Dow Jones). http://online.wsj.com/article/SB10001424052748703940904575395073512989404.html. Retrieved August 3, 2010. 
  42. Steel, Emily and Angwin, Julia (August 4, 2010). "On the Web's Cutting Edge, Anonymity in Name Only". The Wall Street Journal (Dow Jones). http://online.wsj.com/article/SB10001424052748703294904575385532109190198.html. Retrieved August 3, 2010. 
  43. Angwin, Julia and Valentino-DeVries, Jennifer (July 30, 2010). "Analyzing What You Have Typed". The Wall Street Journal (Dow Jones). http://blogs.wsj.com/digits/2010/07/30/analyzing-what-you-have-typed/. Retrieved August 3, 2010. 
  44. Valentino-Devries, Jennifer (July 31, 2010). "What They Know About You". The Wall Street Journal (Dow Jones). http://online.wsj.com/article/SB10001424052748703999304575399041849931612.html. Retrieved August 3, 2010. 
  45. Wingfield, Nick (August 2, 2010). "Microsoft Quashed Effort to Boost Online Privacy". The Wall Street Journal (Dow Jones). http://online.wsj.com/article/SB10001424052748703467304575383530439838568.html. Retrieved August 3, 2010. 
  46. Steel, Emily and Angwin, Julia (August 4, 2010). "One Smart Cookie". The Wall Street Journal (Dow Jones). http://online.wsj.com/article/SB10001424052748704017904575409021400239454.html. Retrieved August 3, 2010. 
  47. Story, Louise and comScore (March 10, 2008). "They Know More Than You Think" (JPEG). The New York Times. http://www.nytimes.com/imagepages/2008/03/10/technology/20080310_PRIVACY_GRAPHIC.html.  in Story, Louise (March 10, 2008). "To Aim Ads, Web Is Keeping Closer Eye on You". The New York Times (The New York Times Company). http://www.nytimes.com/2008/03/10/technology/10privacy.html. Retrieved March 9, 2008. 
  48. 48.0 48.1 Ben-Itzhak, Yuval (April 18, 2008). "Infosecurity 2008 - New defence strategy in battle against e-crime". ComputerWeekly (Reed Business Information). http://www.computerweekly.com/Articles/2008/04/18/230345/infosecurity-2008-new-defence-strategy-in-battle-against.htm. Retrieved April 20, 2008. 
  49. Christey, Steve and Martin, Robert A. (May 22, 2007). "Vulnerability Type Distributions in CVE (version 1.1)". MITRE Corporation. http://cwe.mitre.org/documents/vuln-trends/index.html. Retrieved June 7, 2008. 
  50. "Symantec Internet Security Threat Report: Trends for July-December 2007 (Executive Summary)" (PDF). Symantec Corp.. April 2008. pp. 1–2. http://eval.symantec.com/mktginfo/enterprise/white_papers/b-whitepaper_exec_summary_internet_security_threat_report_xiii_04-2008.en-us.pdf. Retrieved May 11, 2008. 
  51. "Google searches web's dark side". BBC News. May 11, 2007. http://news.bbc.co.uk/2/hi/technology/6645895.stm. Retrieved April 26, 2008. 
  52. "Security Threat Report" (PDF). Sophos. Q1 2008. http://www.sophos.com/sophos/docs/eng/marketing_material/sophos-threat-report-Q108.pdf. Retrieved April 24, 2008. 
  53. "Security threat report" (PDF). Sophos. July 2008. http://www.sophos.com/sophos/docs/eng/papers/sophos-security-report-jul08-srna.pdf. Retrieved August 24, 2008. 
  54. Fogie, Seth, Jeremiah Grossman, Robert Hansen, and Anton Rager (2007) (PDF). Cross Site Scripting Attacks: XSS Exploits and Defense. Syngress, Elsevier Science & Technology. pp. 68–69, 127. ISBN 1597491543. http://www.syngress.com/book_catalog//SAMPLE_1597491543.pdf. Retrieved June 6, 2008. 
  55. O'Reilly, Tim (September 30, 2005). "What Is Web 2.0". O'Reilly Media. pp. 4–5. http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html. Retrieved June 4, 2008.  and AJAX web applications can introduce security vulnerabilities like "client-side security controls, increased attack surfaces, and new possibilities for Cross-Site Scripting (XSS)", in Ritchie, Paul (March 2007). "The security risks of AJAX/web 2.0 applications" (PDF). Infosecurity (Elsevier). Archived from the original on 2008-06-25. http://web.archive.org/web/20080625065122/http://www.infosecurity-magazine.com/research/Sep07_Ajax.pdf. Retrieved June 6, 2008.  which cites Hayre, Jaswinder S. and Kelath, Jayasankar (June 22, 2006). "Ajax Security Basics". SecurityFocus. http://www.securityfocus.com/infocus/1868. Retrieved June 6, 2008. 
  56. Berinato, Scott (January 1, 2007). "Software Vulnerability Disclosure: The Chilling Effect". CSO (CXO Media): p. 7. Archived from the original on 2008-04-18. http://web.archive.org/web/20080418072230/http://www.csoonline.com/article/221113. Retrieved June 7, 2008. 
  57. Prince, Brian (April 9, 2008). "McAfee Governance, Risk and Compliance Business Unit". eWEEK (Ziff Davis Enterprise Holdings). http://www.eweek.com/c/a/Security/McAfee-Governance-Risk-and-Compliance-Business-Unit/. Retrieved April 25, 2008. 
  58. Rebecca Steinberg Herson (April 20, 2008). "Commtouch Unveils New Security Center Web Site - New Web Security Lab Highlights Malware, Phishing Web Categories". http://www.commtouch.com/press-releases/commtouch-unveils-new-security-center-web-site. Retrieved May 25, 2010. 
  59. Preston, Rob (April 12, 2008). "Down To Business: It's Past Time To Elevate The Infosec Conversation". InformationWeek (United Business Media). http://www.informationweek.com/news/security/client/showArticle.jhtml?articleID=207100989. Retrieved April 25, 2008. 
  60. Claburn, Thomas (February 6, 2007). "RSA's Coviello Predicts Security Consolidation". InformationWeek (United Business Media). http://www.informationweek.com/news/security/showArticle.jhtml?articleID=197003826. Retrieved April 25, 2008. 
  61. Duffy Marsan, Carolyn (April 9, 2008). "How the iPhone is killing the 'Net". Network World (IDG). http://www.networkworld.com/news/2008/040908-zittrain.html. Retrieved April 17, 2008. 
  62. 62.0 62.1 62.2 "Web Accessibility Initiative (WAI)". World Wide Web Consortium. http://www.w3.org/WAI/l. Retrieved April 7, 2009. 
  63. "Developing a Web Accessibility Business Case for Your Organization: Overview". World Wide Web Consortium. http://www.w3.org/WAI/bcase/Overviewl. Retrieved April 7, 2009. 
  64. "Legal and Policy Factors in Developing a Web Accessibility Business Case for Your Organization". World Wide Web Consortium. http://www.w3.org/WAI/bcase/pol. Retrieved April 7, 2009. 
  65. "Web Content Accessibility Guidelines (WCAG) Overview". World Wide Web Consortium. http://www.w3.org/WAI/intro/wcag.php. Retrieved April 7, 2009. 
  66. "Internationalization (I18n) Activity". World Wide Web Consortium. http://www.w3.org/International/. Retrieved April 10, 2009. 
  67. Davis, Mark (April 5, 2008). "Moving to Unicode 5.1". Google. http://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html. Retrieved April 10, 2009. 
  68. World Wide Web Consortium (January 26, 2005). "World Wide Web Consortium Supports the IETF URI Standard and IRI Proposed Standard". Press release. http://www.w3.org/2004/11/uri-iri-pressrelease.html. Retrieved April 10, 2009. 
  69. "The 'Deep' Web: Surfacing Hidden Value". Brightplanet.com. Archived from the original on 2008-04-04. http://web.archive.org/web/20080404044203/http://www.brightplanet.com/resources/details/deepweb.html. Retrieved July 27, 2009. 
  70. "Distribution of languages on the Internet". Netz-tipp.de. http://www.netz-tipp.de/languages.html. Retrieved July 27, 2009. 
  71. Alessio Signorini. "Indexable Web Size". Cs.uiowa.edu. http://www.cs.uiowa.edu/~asignori/web-size/. Retrieved July 27, 2009. 
  72. "The size of the World Wide Web". Worldwidewebsize.com. http://www.worldwidewebsize.com/. Retrieved July 27, 2009. 
  73. Alpert, Jesse; Hajaj, Nissan (July 25, 2008). "We knew the web was big...". The Official Google Blog. http://googleblog.blogspot.com/2008/07/we-knew-web-was-big.html. 
  74. 74.0 74.1 "Domain Counts & Internet Statistics". Name Intelligence. http://www.domaintools.com/internet-statistics/. Retrieved May 17, 2009. 
  75. "World Wide Wait". TechEncyclopedia. United Business Media. http://www.techweb.com/encyclopedia/defineterm.jhtml?term=world+wide+wait. Retrieved April 10, 2009. 
  76. Khare, Rohit and Jacobs, Ian (1999). "W3C Recommendations Reduce 'World Wide Wait'". World Wide Web Consortium. http://www.w3.org/Protocols/NL-PerfNote.html. Retrieved April 10, 2009. 
  77. Nielsen, Jakob (from Miller 1968; Card et al. 1991) (1994). "Usability Engineering: Response Times: The Three Important Limits". Morgan Kaufmann. http://www.useit.com/papers/responsetime.html. Retrieved April 10, 2009. 

References

External links